Sensor web

The concept of the "sensor web" is a type of sensor network that is especially well suited for environmental monitoring.^[1][2][3] The phrase the "sensor web" is also associated with a sensing system which heavily utilizes the World Wide Web. OGC's Sensor Web Enablement (SWE) framework defines a suite of web service interfaces and communication protocols abstracting from the heterogeneity of sensor (network) communication.^[4]

Contents 1 Definition 2 Characteristics of Delin's sensor web architecture 3 See also 4 References 5 Further reading 6 External links

Definition

The term "sensor web" was first used by Kevin Delin of NASA in 1997,^[5] to describe a novel wireless sensor network architecture where the individual pieces could act and coordinate as a whole. In this sense, the term describes a specific type of sensor network: an amorphous network of spatially distributed sensor platforms (pods) that wirelessly communicate with each other. This amorphous architecture is unique since it is both synchronous and router-free, making it distinct from the more typical TCP/IP-like network schemes. A pod as a physical platform for a sensor can be orbital or terrestrial, fixed or mobile and might even have real time accessibility via the Internet. Pod-to-pod communication is both omni-directional and bi-directional where each pod sends out collected data to every other pod in the network. Hence, the architecture allows every pod to know what is going on with every other pod throughout the sensor web at each measurement cycle. The individual pods (nodes) were all hardware equivalent^[1] and Delin's architecture did not require special gateways or routing to have each of the individual pieces communicate with one another or with an end user. Delin's definition of a sensor web was an autonomous, stand-alone, sensing entity – capable of interpreting and reacting to the data measured – that does not necessarily require the presence of the World Wide Web to function.^[6] As a result, on-the-fly data fusion, such as false-positive identification and plume tracking, can occur within the sensor web itself and the system subsequently reacts as a coordinated, collective whole to the incoming data stream. For example, instead of having uncoordinated smoke detectors, a sensor web can react as a single, spatially-dispersed, fire locator.

The term "sensor web" has also morphed into sometimes being associated with an additional layer connecting sensors to the World Wide Web.^[7][8][9] The Sensor Web Enablement (SWE) initiative of the Open Geospatial Consortium (OGC) defines service interfaces which enable an interoperable usage of sensor resources by enabling their discovery, access, tasking, as well as eventing and alerting.^[10] By defining standardized service interfaces, a sensor web based on SWE services hides the heterogenity of an underlying sensor network, its communication details and various hardware components, from the applications built on top of it.^[5] OGC's SWE initiative defines the term "sensor web" as an infrastructure enabling access to sensor networks and archived sensor data that can be discovered and accessed using standard protocols and application programming interfaces. Through this abstraction from sensor details, their usage in applications is facilitated.

Characteristics of Delin's sensor web architecture

Delin designed a sensor web as a web of interconnected pods. All pods in a sensor web are equivalent in hardware (there are no special "gateway" or "slave" pods). Nevertheless, there are additional functions that pods can perform besides participating in the general sensor web function. Any pod of a sensor web can be a portal pod and provides users access to the sensor web (both input and output).^[11] Access can be provided by RF modem, cell phone connections, laptop connections, or even an Internet Server. In some cases, a pod will have an attached removable memory unit (such as a USB stick or a laptop) that stores collected data.^[12][13]

The term of mother pod refers to the pod that contains the master clock of the synchronous sensor web system. The mother pod has no special hardware associated with it, its designation as a mother is merely based on the ID number associated with the pod.^[14] Often the mother pod serves as a primary portal point to the Internet, but this is done only for deployment convenience. Early papers referenced the mother pod as "a prime node" if it additionally contained special hardware for a particular type of input/output device (say an RF modem).

Because of the inherent hopping of data within a sensor web, a pod with no attached sensors can be deployed as a relay with the single purpose of facilitating communication between the other pods and to expand the communication range to a particular end-point (such as a mother pod).^[13] Sensors can be attached to relay pods at a later time and relays can also serve as portal pods.

Each pod usually contains:^[2]

• one or more sensor leading to one or more data channel,
• a processing unit such as a micro-controller or microprocessor,
• a two-way communication component such as a radio and antenna (radio ranges are typically limited by government spectrum requirements; unlicensed bands will allow for communication of a few hundred yards in unobstructed areas, although line of sight is not a requirement),
• an energy source such as a battery coupled with a solar cell,
• a package to protect components against sometimes harsh environment,

Each pod also typically requires a support such as a pole or tripod.^[13] The number of pods may vary, with examples of sensor webs with 12 to 30 pods.^[11] The shape of a sensor web may impact its usefulness, for instance a particular deployment^[13] made sure each pod was in range to communicate with at least two other pods. Sensor web measurement cycles have typically been between 30 seconds and 15 minutes for deployed systems thus far.^[15]

Sensor webs consisting of pods have been deployed that have spanned miles and run continuously for years.^[16] Sensor webs have been fielded in harsh environments (including deserts, mountain snowpacks, and Antarctica)^[17] for the purposes of environmental science and have also proved valuable in urban search and rescue and infrastructure protection.^[18] The technology is not only monitoring the environment but sometimes also controlling the environment by actuating devices.^[11]

See also

• Observations and Measurements
• Open Geospatial Consortium
• SensorML

References

Further reading

• Sensor Webs, K.A. Delin, S.P. Jackson, and R.R. Some NASA Tech Briefs 1999, 23, 90 [1] open access publication.

• The Sensor Web: Distributed Sensing for Collective Action, Kevin A. Delin Sensors Online July 2006, 18 [2] open access publication.

• The Sensor Web: A Distributed, Wireless Monitoring System, Kevin A. Delin Sensors Online April 2004, 21 [3] open access publication.

• New Generation Sensor Web Enablement, Arne Bröring, Johannes Echterhoff, Simon Jirka, Ingo Simonis, Thomas Everding, Christoph Stasch, Steve Liang, Rob Lemmens Sensors 2011, Volume 11, Number 3, 2652-2699 [4] open access publication.

• Environmental Studies with the Sensor Web: Principles and Practice, Kevin A. Delin, Shannon P. Jackson, David W. Johnson, Scott C. Burleigh, Richard R.Woodrow, J. Michael McAuley, James M. Dohm, Felipe Ip, Ty P.A. Ferré, Dale F. Rucker, Victor R. Baker Sensors 2005, 5, 103-117 [5] open access publication.

• OGC Sensor Web Enablement: Overview and High Level Architecture, Botts, Percivall, Reed, and Davidson [6] OGC White Paper, July 2006 open access publication.

• Open Sensor Web Architecture: Core Services,Xingchen Chu, Tom Kobialka, Bohdan Durnota, and Rajkumar Buyya, Proceedings of the 4th International Conference on Intelligent Sensing and Information Processing (ICISIP 2006,IEEE Press, Piscataway, New Jersey, USA, ISBN 1-4244-0611-0, 98-103pp), Dec. 15-18, 2006, Bangalore, India. [7] open access publication.

• A SensorWeb Middleware with Stateful Services for Heterogeneous Sensor Networks,Tom Kobialka, Rajkumar Buyya, Christopher Leckie, and Rao Kotagiri, Proceedings of the 3rd International Conference on Intelligent Sensors, Sensor Networks and Information Processing (ISSNIP 2007, IEEE Press, Piscataway, New Jersey, USA), Dec. 3-6, 2007, Melbourne, Australia. [8] open access publication.

External links

• SensorWare Systems, Inc. – A company spun-out of the NASA Sensor Webs Project and providing sensor web technology especially for agricultural, life safety, and remediation needs. Live, real-time streaming data from deployed systems may also be found on this site.
• Sensor Web Alliance – An organization that is developing a collaborative research platform called the Sensor Web Alliance (SWA). The aim is to pool resources in the SWA, coordinate research and allow participating organisations to share IP, which will spread risk and lower the cost of entry.
• SenseWeb Project – A Microsoft Research project that lets users visualize and query real-time data using a geographical interface such as Windows Live Local and allows data owners to easily publish their live data using a web service interface.
• GeoSensor Web Lab, University of Calgary – A university research lab that is developing a GIS infrastructure for the Sensor Web and its applications. Several sensor web applications have been developed and deployed for environmental and agricultural applications. Project information, publications, and demo videos can be found on this site.
• 52°North – An open partnership organization that interoperable web services and data encoding models, which constitute the technical building blocks of Spatial Data Infrastructures (SDIs).
• SWSL at the Institute for Geoinformatics (IFGI) of the University of Muenster – The Sensor web, Web-based geoprocessing, and Simulation Lab (SWSL) is a university lab working on the building blocks of the geosensor web to make all different kinds of sensors discoverable, accessible and taskable in an interoperable way.
• OGC SWE – Since 2002, the Open Geospatial Consortium (OGC) has had a focused Sensor Web Enablement (SWE) activity. From the OGC perspective, a sensor web refers to web accessible sensor networks and archived sensor data that can be discovered and accessed using standard protocols and application program interfaces (APIs).
• Open SensorWeb Architecture Project – The project focuses on the development of service-oriented middleware for SensorWeb that integrates sensor networks and distributed computing environements such as computational Grids.
• Sensorweb Research Laboratory – A research lab at Georgia State University, developing sensor web systems and applying them to scientific and social applications, such as environment monitoring, smart environments, and smart grid applications.
• SEPS Project – The Self-adaptive Earth Predictive System (SEPS) concept combines Earth System Models (ESM) and Earth Observations (EO) into one system through standard Web services. This is a collaborative project that consists of scientists from the Center for Spatial Information Science and Systems (CSISS) of George Mason University, NASA GSFC, and UMBC.
• Semantic Sensor Web – The SSW project is an attempt to annotate sensor data with semantic metadata to provide contextual information essential for situational awareness. In particular, it is an approach to annotating sensor data with spatial, temporal, and thematic semantic metadata.

Wireless Sensor Network Operating systems Contiki · ERIKA Enterprise · Nano-RK · SOS · TinyOS  · LiteOS  · NanoQplus Industry standards ANT · 6LoWPAN · DASH7 · ONE-NET · ZigBee · Z-Wave · Wibree · WirelessHART  · 802.15.4 Programming languages C  · LabVIEW · nesC Hardware EcoWizard · FLEX Mini · MICAz · Iris Mote · NeoMote · Sun SPOT Software TinyDB · TOSSIM · NS-2 · Cooja · LinuxMCE Applications Key distribution · Location estimation · Sensor Web · Telemetry Protocols AODV · DSR · TSMP Conferences/Journals SenSys · IPSN · EWSN · SECON · INSS